home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000356_kb@cs.umb.edu_Thu Mar 10 01:22:21 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
2KB
Received: from ra.cs.umb.edu by cs.umb.edu with SMTP id AA06015
(5.65c/IDA-1.4.4 for <tex-k-exp@cs.umb.edu>); Thu, 10 Mar 1994 08:32:17 -0500
Received: by ra.cs.umb.edu id AA19043
(5.65c/IDA-1.4.4 for tex-k); Thu, 10 Mar 1994 06:22:21 -0500
Date: Thu, 10 Mar 1994 06:22:21 -0500
From: "K. Berry" <kb@cs.umb.edu>
Message-Id: <199403101122.AA19043@ra.cs.umb.edu>
To: tex-k@cs.umb.edu
Subject: kpathsea versions
Tim asks if kpathsea is supposed to be the same in all the distributions.
Well, I only have one set of development sources (that's more or less
the whole point, after all). So when I make simultaneous releases, the
kpathsea directory should be identical in all of them (if it isn't,
there's an error in my distribution procedures).
But I continue to develop the stupid thing, so releases made at
different times will likely not have the same directory. The kpathsea
that was distributed with web2c 6.1 is older than the one in the current
*k drivers.
You can't mix and match effortlessly, either -- trying to compile web2c
with the new kpathsea (or the drivers with the old one) almost certainly
won't work without source changes. Since no one (that I know of) is
doing any work with kpathsea besides me, I am 100% unconcerned with
backward compatibility in the library interface at this point. I'm still
finding plenty of improvements to make, after starting this project
umpteen years ago.
I do have a limited number of things on the wishlist to do. When I've
implemented them, it might make sense to be concerned with
compatibility, and to write documentation for the interface, etc.